Labels:text | paper | font | letter | screenshot | document OCR: A Software Build Process Checklist Complete Any Pending Changes Search for place-holder comments that still need to be replaced with code. Update the file and function prologs and add other necessary comments. Verify that all new code meets the established coding standards. Check the spelling of all new user-interface text (prompts, error messages, etc.). Create or modify appropriate unit test drivers and run them. Remove extraneous debugging code. Turn off debugging compiler switches. "Check in" Files "Check in" all modified files to the version control system (VCS). Compare files that might have been modified without having been checked out first and resolve conflicts. Plan the Build Compile a list of significant changes (compare the new code base to the code base from the previous build and/or confer with VCS logs, checked off task lists, status reports, etc.). Determine if any changes will require special handling during this build (because of changes to data files, .INI files, etc.). Prepare a build memo informing users of the significant changes, standard or special installation notes, known problems with the new build, etc. Make o Build Candidate Check out a fresh set of source code files. Update the build number (and/or other relevant numbers andfor dates: version, revision, release) as appropriate. Insure that the proper build environment is in place. Run the "Make" scripts, batch files, etc. to build all of the deliverables (executables, run-time libraries, etc.). Verify the Build Run whatever build tests have been established (a non-stop sequence of unit test-drivers, an automated integration test, a manual testing checklist, etc.). Inspect the deliverables for missing files, wrong file names, unusually sized files, etc. Publish the Build Transfer the new deliverables to the delivery medium (network volume, distribution diskettes, etc.) as appropriate. Finalize and distribute the build memo. Monitor at least one installation to check the build memo instructions. Figure 2: A generic checklist for the process of building the pro- gram deliverable(s).
